AI PlayBook Series · Playbook 03

From "Where Do I Even Start?"
To "It Already Did It."

It's 9am on a Tuesday. Your phone buzzes once. Not forty emails to dig through. One message. Your inbox, your calendar, your Drive folder, and your customer list, already checked overnight. That's the whole goal here: one real automation, built by you, that runs without you.

Every feed right now has someone showing off ten automations built in a weekend. Most of those are one demo video sitting on top of nine broken pieces. This gets you one automation that actually finishes. The rest can wait.

⏱ One weekend, a few hours at a time
Scroll
💡 New to Codex? Read Playbook 02 first. It shows you what this thing actually does. Come back here once you're ready to build the real thing.

Right now you've probably got a dozen tabs open about AI and zero automations actually running. That's normal. Everyone's talking about this. Almost nobody's finished one.

This isn't a guide to automate your whole business by Sunday. It's the order that gets you one real automation, the kind that checks your email, your calendar, your Drive, and your customer list every morning, then reports back so you make decisions faster. Build that one thing first.

Six moves below are tagged Critical. Skip one and the failure won't look like a failure. It'll look like Codex being "slow," when really a wire never got connected. Some moves take three seconds. The whole setup takes a weekend.

Before You Start

Get the boring stuff right first

01

Confirm Your Plan

You need the $100-a-month ChatGPT plan or higher. The free version is like trying to run a moving truck on a moped's gas tank. It won't make it far. Double check you're logged into the right account too, especially on a shared laptop.

02

Pick One Cloud Folder

Drive, Dropbox, or GitHub. Pick one and stick with it. This becomes Codex's entire desk. Split work across two folders and it spends half its time looking for the stapler.

03

Block The Time

This takes a weekend, not an afternoon. Rushing it now is how people end up rebuilding the whole thing in week three.

01
⏱ 2–4 hours

The Infrastructure Layer

Skip the breaker box when you wire a house, and here's what actually happens: you run the toaster and the microwave at the same time, and the kitchen goes dark. Nothing's broken. The wiring's just incomplete. These three moves are Codex's breaker box.

Set Up The Sandbox

Critical

The sandbox is where Codex actually does its work. Miss one of these settings and it stalls out mid-task, the same way a half-wired kitchen loses power the moment you run two things at once.

  • Cloud storage connected to your one folder
  • Full access turned on, not read-only
  • "Prevent Sleep While Running" switched ON
  • Speed set to Standard
  • Computer Use and Browser Use both ON
  • Suggested Prompts switched OFF
  • Sandbox mode set to full access for real work, not read-only

Real estate example: A brokerage running read-only mode watches Codex spot every calendar conflict, then just sit there. Full access is what lets it actually do something about it.

Configure The Basics

Set work mode to operational, not experimental. Keep speed on Standard. Turbo burns through your token budget for the same result, like paying for express shipping on something that wasn't urgent.

Set Permissions Deliberately

Critical

Permissions are the keys to your email, files, and calendar. Hand them over on read-only, and Codex can see the mess but can't touch it, like a contractor who can point at the wiring but isn't allowed to pick up a tool. Grant full access, and test it before you move on. Don't just assume it worked.

02
⏱ 3–5 hours

Capabilities & Access

Now you flip the switches. One of them fails quietly. The last move here catches it before it costs you a week.

Turn On Computer Use & Browser Use

Computer Use lets Codex click around inside apps on your machine. Browser Use lets it open websites, log in, and pull data, like a very fast, very literal helper. Both are optional. Both are worth turning on.

Know Your Token Budget

Tokens work like data on a phone plan. Burn through them on one giant task and you're stuck waiting on the next cycle. Short tasks, more often, stretch further than one long one.

Build 3–5 Workspaces, Not 50

Give Codex a few named folders for different parts of your business. Past 10 or 15, it starts losing track of which one does what, the same way a desk buried in fifty sticky notes stops being useful.

An HVAC company might run Dispatch, Quoting, and Billing. A restaurant might run Reservations, Supplier Orders, and Marketing.

Connect 4–6 Plugins, Not Every Plugin

Start with Gmail, Drive, and Calendar. Add one more for your business: Stripe, QuickBooks, or your CRM, the tool that tracks your customers and deals. Every extra plugin is one more thing that can quietly break, so skip the urge to connect the whole list.

Prove Every Plugin Actually Works

Critical

"Connected" doesn't mean working, the same way a light switch can flip without the bulb turning on. Run this on every plugin before you build anything on top of it.

Copy This Prompt
Before I trust any of my connected tools, prove each one works. For every plugin I have connected, do this: 1. Gmail: read my last 5 emails and tell me the subject lines. 2. Google Drive: list the files in my [folder name] folder. 3. Calendar: tell me what's on my schedule next week. 4. [Stripe / QuickBooks / your CRM]: show me my last 3 records. If any of these fail or come back empty, tell me exactly which one and stop there. Don't guess or invent data to fill the gap.
03
⏱ 8–15 hours

Building Operational Context

This is where Codex stops guessing and starts actually knowing your business. It's the longest phase here. Everything after this runs without you.

Activate Skills: Start With One

There's a library of pre-built skills already sorted by job: onboarding, sales, operations, content. Don't write your own from scratch. Open one, swap in your details, and add a second once the first one actually works.

Run The Permissions Audit Skill

Critical

Run this before anything else in this phase. It checks your whole setup for what you might have missed in Phase 01 and 02: broken plugins, wrong permissions, missing settings. Think of it as the home inspector who shows up before you move the furniture in.

Copy This Prompt
Run a full audit of my current setup before I build anything else on top of it. Check: - Every plugin I have connected, and whether it can actually retrieve data - My file permissions in [your cloud storage] - My sandbox settings: sleep prevention, approval policy, full access List every problem you find, in plain English, ranked from most urgent to least urgent. Don't tell me everything looks fine unless you actually checked each item above.

Let Codex Read Your ChatGPT History

Scroll back three to six months through what you've already asked ChatGPT. That's basically your business diary. Let Codex read it instead of hiding it.

Run Business Intelligence Gathering

Critical

This is the move that turns Codex from a stranger into someone who actually works there. It reads your real email, files, calendar, and payments instead of asking you to explain your business in a paragraph. Let it run the full hour. Don't pull it out early, like a cake that isn't done yet.

Copy This Prompt
Read through my real business data instead of asking me to describe my business to you. Go through: - My email and message history - My [cloud storage] files - My calendar - My [Stripe / accounting tool] data Build a summary of how my business actually runs: busiest days, biggest clients or jobs, recurring deadlines, and the kind of decisions I make most often. Base this only on what you find. Flag anything you're unsure about instead of guessing.

When it finishes, read what it says it learned. If it's wrong about how your business runs, fix it now, before that mistake gets baked into every automation you build next.

Organize Files The Way Agents Read Them

Critical

Agents don't think the way you do. They don't know that V2_FINAL_actual_final.docx is the real one. Flatten your folders to three or four levels, pick one naming style, and group things by the job an agent does, not by department. Messy files in here means messy answers out.

Build The Agent Home Base

Critical

One folder holds everything every agent needs to know about your business: your price list, who's allowed to see what, and a log of which agent touched which file and when. Build this only once your files are already clean. Messy files in, messy coordination out.

Set Up Voice Prompts

Talking to Codex beats typing when you want something thought through, like a memo, not a quick task. It costs more tokens, so save it for when it actually matters.

Turn On Your First Automation

Critical

Pick one task that proves its worth in the first week. Daily email sorting is the easiest win for most service businesses. Test it on a slow day first, and watch the first three runs yourself before you trust it to run alone.

Copy This Prompt
Set up a daily automation that runs every morning at 9am. Each time it runs: 1. Read all new emails since the last run 2. Sort them into folders: Leads, Existing Clients, Suppliers, Urgent, Everything Else 3. Flag anything mentioning a quote, a complaint, or a same-day request as Urgent 4. Send me a two-line summary: how many new emails, and how many are Urgent Run this on a test day first. Show me the results before you set it to repeat automatically.

Once it's reliable for a week, add a second one. Stack five at once, and you won't know which one broke when something goes wrong.

The Three Checkpoints That Catch Silent Failures
1After permissions are set in Phase 01. Run the Proof Protocol before you connect a single plugin.
2After the Permissions Audit runs in Phase 03. Fix every flag it finds before you keep going.
3After Business Intelligence Gathering finishes. Read what Codex learned about your business and fix anything wrong before you build on top of it.

You don't need ten automations. You need one that finishes.

Pick one phase. Get it right. Check it before you touch the next one. In a few weeks, you're not the person with twelve tabs open anymore. You're the one whose phone buzzed once this morning, because the thing already did it.

Questions? Want more of this? Follow me on LinkedIn or send a DM.